i18n(ja): "Quick Start" Section #3111
Conversation
✅ Deploy Preview for tauri-v2 ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
I'll come back to review with google translate. It may take a few days, don't need to "Update branch" until then. It would be best if we'd have someone fluent to review, as imagine you intend to continue translating |
|
@vasfvitor Also Sorry to say that I mistakenly pushed the uncompleted drafts of the next section "Concept", which still need to correct link information (jp to ja etc.) and translation updates. Is it safe to reset or revert them? They will probably cause format errors again. |
|
@J1-takai @vasfvitor Since this is my first time helping to translate documentation in the community, I would appreciate it if you could tell me where to start. |
vasfvitor
changed the title
It's all good
Ideally you should have a feature branch to each translation to avoid this. There's a safe way to undo and not lose your changes, if you're be able you can do it yourself, else manually copy those drafts translations to another branch and let me know when you do, so I can revert it myself. Either way have a backup.
Considering that you said that "you're not a programmer", and I'm not sure what text editor you're using or if you're familiar with the concept, but generally they have some sort of "search and replace". So basically you could try search |
|
@penginnu hi again, thanks for your help. You can start at this PR just ignore those files listed here those files are to be reviewed: General guidelines https://github.com/tauri-apps/tauri-docs/blob/4f3f5012e5a463653c8f61861de9ea7eba8727f5/.github/TRANSLATING.md The main point is to avoid typos, sentences that are too far from the original meaning, unrelated/uneeded changes |
|
@vasfvitor Thank you!
I have some knowledge of astrojs, tauri and nodejs, but I am not familiar with translations, so I may cause you some inconvenience ... |
|
Thx for ur quick actions. Since I am a non-programmer (& retired old man), @penginnu-san's reviews on the technical aspect of my translations are highly appreciated. Regarding a feature branch idea, this may be a good idea to proceed the large document site like Tauri. I will check how to do it. |
Co-authored-by: pengin.nu <[email protected]>
Co-authored-by: pengin.nu <[email protected]>
Co-authored-by: pengin.nu <[email protected]>
Co-authored-by: pengin.nu <[email protected]>
|
@J1-takai have you managed to copy the "concept" page drafts to a new branch? |
Format errors will happen regardless, it's just a way to ensure we have a default formatting, so we can track only real changes, not formatting. If you can manage to, run |
|
@vasfvitor Yes, I copied the concept files into the separate folder. Also I am now working using the new branch "Concept-ja". As for running |
|
basically you open a terminal at the cloned repository and run |
This reverts commit 26fb977.
|
@vasfvitor |
|
you should be able to open any terminal and enter |
|
@vasfvitor Thank you for your many advice, but the problem still exists - this time I tried the node/pnpm in the local directory of Tauri-Docs, but the error message "pnpm CLI is missing" occurred - in the local directory Node -v works but pnpm -v failed. I decided to put this issue aside for the time being and proceed the translation work. Thank you again for your help. |
|
@vasfvitor @penginnu |
i18n (JP) Translation for "Quick Start" section
This is a trial translation work for "Tauri Doc 2.0 Japanese Version" from the scratch. If there are any similar activities already on-going, please disregard this pull request. If not, my drafts would need technical proof-reading as I have almost no knowledge on programming - my only programming experiences were introductory courses for FORTRAN and COBOL using punch cards data loading some 40 years ago, HA HA! No rush - Please take your time.